Import and Export let you move your Glublers in and out of Glubler as a CSV file. Use it to back up your collections, to move them to a different account, or to rebuild a structure you already have elsewhere.
Import and Export work with the structure of your collections and the websites inside them. Anything you have glued is included.
Both live under Settings → Data, on the same screen. There is an Import tab and an Export tab, and you switch between them.
You must be signed in, since the file is tied to your account.
Glubler uses a simple CSV file with four columns:
| Column | Required | What it holds |
|---|---|---|
Url |
Yes | The website address |
Title |
No | The name to show for the site |
Hierarchy |
No | Which collection the site belongs in |
Favicon |
No | Site icon. Glubler fills this in for you |
Your file needs a header row, and the column names must match those above. The order of the columns does not matter, and capitalisation is ignored, so url and URL are both fine.
Only Url is actually required. The other three can be left out entirely, and Glubler will look the details up itself.
This is the column that matters most. It tells Glubler where each site should go, using the names of your collections joined together.
A top-level collection is just its name. To put a site inside a Subglubler, join the names with >:
Glubler creates any collections it needs as it goes. You do not have to build the structure first and then add the sites to it.
If a collection named in the path already exists, Glubler uses it rather than making a second one. So importing a file with Travel > Japan into an account that already has those collections will add the sites to the collections you already have.
Note: The exported file uses > between names. Glubler also understands | and / if you are writing the file by hand.
glublers_export.csvThe export always covers your whole account: every Glubler, every Subglubler, and every website glued into them.
One row per glued website, with its collection shown in the Hierarchy column. Site icons are included where Glubler already has one stored, and left blank where it does not.
The export is built from the websites inside your collections, so a collection with nothing glued into it produces no rows and will not appear in the file. If you have collections you have not filled yet, they will not survive an export and re-import. Keep your own note of them if they matter.
If your account has no glued websites at all, the download still succeeds. You will get a file containing just the header row and nothing else.
When you are done, Glubler shows how many websites were added, how many were skipped, and how many could not be read. Read that summary before assuming the import worked.
Files can be large, up to about 100 MB, and a big import can take a while. That is normal, and the import will not time out on you.
So there are no surprises, here is exactly what happens to each row.
Glubler checks every website against the ones already in your account, across all of your collections. Anything already saved is skipped.
Note: This check covers your whole account, not just the collection named in the file. If a site is already in "Reading" and your file puts it under "Travel", it is skipped rather than added to the second collection. To move a site between collections, remove it from one and glue it to the other.
A row is skipped if the Url is empty or is not a valid web address. Each one is counted separately and named in the summary, so you can go back and fix your file.
A bad row does not stop the rest of the file. Glubler works through every row it can and reports what it could not use, so a single typo will not cost you the whole import.
Import adds to your account. It does not wipe your existing Glublers, and it does not update collections that are already there. To start fresh, delete what you want removed first, or import into a different account.
| What you import | Free | Pro |
|---|---|---|
| A flat list of websites | Yes | Yes |
| Into existing collections | Yes | Yes |
| Into Subglublers | — | Yes |
Note: A file counts as "nested" as soon as any row's Hierarchy contains a >, a |, or a /. On a Free plan, such a file is rejected as a whole before anything is imported, rather than importing the flat rows and stopping at the nested ones.
Url and Hierarchy columns only. Glubler will fill in titles and icons itself, and it does a better job than a guessed value.Not from the Settings screen. The export button always produces a file for your whole account. If you need a single collection, you can edit the exported file and keep the rows you want.
No. Glubler matches collections by name along the path in the file. If the collection already exists, your sites are added to it instead of a second copy being made.
No. Websites you already have saved anywhere in your account are skipped, so re-importing the same file will not add anything the second time.
No. Glubler creates the collections it needs regardless of the order the rows appear in, and the order you glued the sites is not preserved.
Yes. Export from the old account, then import the file while signed in to the new one. Remember that empty collections are not carried across, and that a nested file needs Pro on the receiving account.
Nothing. Import only adds. Your current collections, their contents, and your followers are untouched.
Most often because that site is already in your account, which Glubler treats as a duplicate. The summary tells you how many were skipped for this reason. If a row failed instead, the reason is listed against that row.